…+ Overlay A #4 (PR #162)

Two PRs this tick, both self-scheduled free work per the
2026-04-23 scheduling-authority rule:

- PR #162 — Overlay A #4: external-signal-confirms-internal-
  insight discipline migrated per-user → in-repo
- PR #163 — P1 BACKLOG row for fresh-session quality research
  (Aaron 2026-04-23 directive)

Queue now 1 remaining Overlay A migration
(semiring-parameterized-zeta). Fresh-session gap research
cites soulfile-staged-absorption (PR #156) as the designed
fix; research would validate that thesis.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…filed

PR #163 (fresh-session-quality research BACKLOG): 3 Copilot
findings on references-to-not-yet-merged / references-to-
per-user-memory. Fixed at source; 3 threads resolved; rebased.

New P3 row: Rational Rose research (Aaron 2026-04-23 low-
priority directive) — UML model-as-source-of-truth lineage;
research pointer; no adopt commitment.

Both landed on PR #163's branch (same BACKLOG.md edits).

4 session PRs merged; 3 armed; 12 still open.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Aaron: "backlog is uml modeling useful for the factory and
what tools would it require us map?"

Filed as P3 row with two-question research pointer (utility
vs existing OpenSpec + formal-spec discipline; tooling-map
for factory-technology-inventory). First-pass recommendation:
Mermaid as factory-aligned default (git-native, zero
toolchain). Auto-merge armed.

Adjacent to Rational Rose P3 row (PR #163) — both will sit
together on merge; row #54 first firing likely flags for
consolidation consideration.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Aaron 2026-04-23: "backlog is uml modeling useful for the
factory and what tools would it require us map?"

Two-question research pointer:
1. Utility — does UML add value on top of OpenSpec + formal
   specs (TLA+ / Lean / Z3 / FsCheck / Alloy)?
2. Tooling-map — if we adopt, what tools would the factory
   inventory (PlantUML / Mermaid / draw.io / Structurizr /
   Rational Rose lineage)?

Composes with:
- Rational Rose P3 row (adjacent when PR #163 merges)
- docs/FACTORY-TECHNOLOGY-INVENTORY.md (PR #170 target)
- OpenSpec workflow (spec-as-source-of-truth already in
  place)
- Formal-spec stack

First-pass recommendation (to validate): Mermaid is the
factory-aligned default (git-native, zero toolchain, GitHub
renders natively); heavy UML tools likely over-scoped.

Research note under docs/research/uml-modelling-for-the-
factory-YYYY-MM-DD.md when prioritised. No adopt commitment.
No deadline. Effort S first-pass; M if adopting.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…#173)

Aaron 2026-04-23: "backlog is uml modeling useful for the
factory and what tools would it require us map?"

Two-question research pointer:
1. Utility — does UML add value on top of OpenSpec + formal
   specs (TLA+ / Lean / Z3 / FsCheck / Alloy)?
2. Tooling-map — if we adopt, what tools would the factory
   inventory (PlantUML / Mermaid / draw.io / Structurizr /
   Rational Rose lineage)?

Composes with:
- Rational Rose P3 row (adjacent when PR #163 merges)
- docs/FACTORY-TECHNOLOGY-INVENTORY.md (PR #170 target)
- OpenSpec workflow (spec-as-source-of-truth already in
  place)
- Formal-spec stack

First-pass recommendation (to validate): Mermaid is the
factory-aligned default (git-native, zero toolchain, GitHub
renders natively); heavy UML tools likely over-scoped.

Research note under docs/research/uml-modelling-for-the-
factory-YYYY-MM-DD.md when prioritised. No adopt commitment.
No deadline. Effort S first-pass; M if adopting.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…tive + first test

First Otto-attributed tick. Three directive absorptions:

(a) Loop agent named Otto, role Project Manager per Aaron
    2026-04-23 directive. Otto IS Claude-in-autonomous-loop-
    without-a-persona-hat; sibling to Kenji/Aarav/etc.
    Not a new SKILL.md. Prior "unnamed-default (loop-agent)"
    attributions (Showcase, Anima) reattribute to Otto.

(b) Claude Cowork fact-check: Google hallucinated `-w`
    workstream mode. Real flag is `--worktree` (git worktree
    isolation). Cowork is a separate Anthropic product
    (Claude Desktop / web), not a CLI mode. `/loop` already
    inherits all harness features. No restart needed.

(c) NSA (New Session Agent) persona = first-class directive.
    Extends PR #163 passive monitoring → active testing.
    5-prompt test set, 3 configurations (baseline /
    NSA-default / NSA-worktree), 5 metrics.

First NSA test run same-tick: `claude -p --model haiku-4-5`
cold-start query found Zeta project identity correctly but
FAILED to find Otto — gap identified (MEMORY.md had no
pointer to new per-user memories). Fixed same-tick.
Concrete demonstration: NSA testing catches substrate gaps
that current-session agents miss.

Attribution: Otto (loop-agent PM hat) for hat-less work.
No persona hats worn this tick.

Per-user memories filed:
- project_loop_agent_named_otto_role_project_manager_2026_04_23.md
- reference_claude_code_w_flag_is_worktree_not_workstream_cowork_is_separate_product_2026_04_23.md
- feedback_new_session_agent_persona_first_class_experience_test_fresh_sessions_including_worktree_2026_04_23.md

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>